Hierarchical Chunking of Objects in a Distributed Storage System

ABSTRACT

Placement of object replicas in a distributed storage system includes, at a first instance, opening a journal for storage of object chunks. An object is received, which comprises one or more chunks. Each chunk comprises one or more storage blocks. The blocks for a single chunk are stored in a single journal. Global metadata for the object is stored, which includes a list of chunks for the object. Local metadata for the chunk is stored, which includes a block list identifying each block of the plurality of blocks. The local metadata is associated with the journal. The journal is later closed. The journal is subsequently replicated to a second instance. The global metadata is updated to reflect the replication, whereas the local metadata is unchanged by the replication.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 14/142,706, filed Dec. 27, 2013, entitled “Hierarchical Chunking of Objects in a Distributed Storage System,” which is incorporated by reference herein in its entirety.

This application is related to U.S. patent application Ser. No. 13/927,010, filed Jun. 25, 2013, entitled “Grouping of Objects in a Distributed Storage System Based on Journals and Placement Policies,” which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

The disclosed implementations relate generally to distributed storage systems, and more specifically to splitting objects into chunks and storing the chunks hierarchically.

BACKGROUND

Large-scale data storage has shifted from a central-service architecture to distributed storage systems. Distributed storage systems built from commodity computers can deliver high performance, availability, and scalability at a fraction of the cost compared to monolithic disk arrays. Data is replicated across multiple instances of the distributed storage system at different geographical locations, thereby increasing availability and reducing network distance from clients.

In a distributed storage system, objects are dynamically placed in (i.e., created in, deleted from, and/or moved to) various instances of the distributed storage system based on constraints. There are few existing techniques for efficiently placing objects that are subject to constraints in a planet-wide distributed storage system that stores trillions of objects and petabytes of data, and includes dozens of data centers across the planet.

New visualization, multimedia, and other data-intensive applications use very large objects, which may be hundreds of gigabytes or larger. Managing such very large objects create additional complexities for a distributed storage system. First, uploading such an object into a distributed storage system is typically done in a streaming mode, splitting the object into chunks and writing each chunk individually. This can impose long delays for uploading, which is exacerbated by potential client and server failures. Moreover, chunks may be aggregated into larger shards for better operational efficiency. The terms “shard” and “journal” may be used interchangeably herein. Consequently, efficient upload of large objects is becoming increasingly important for the storage industry being driven by the needs of large-scale systems that allow clients to connect to any cluster available at a time. In addition, the volume of metadata for a single object (e.g., 25000 chunks for a 100 gigabyte file, where each chunk is 4 megabytes) makes replication and compaction less efficient.

SUMMARY

Disclosed implementations distribute the upload of large objects to multiple storage locations simultaneously. As used herein, the storage locations are referred to as “shards,” “aggregated shards,” or “journals.” This scheme is implemented by splitting a large object into multiple chunks, each of which can be uploaded to a different storage cluster (which may be in distinct geographic locations). If a shard becomes unavailable during upload, (e.g., because the shard is “full” or the instance where the shard is stored goes down), the client switches to a new shard, which may be in a different cluster. This scheme does not require sticking with the same shard once started. A finalized object is represented by an ordered list of chunk references.

In some schemes, a chunk is the basic unit of storage, and the location of each chunk is stored in global metadata. For very large objects, this scheme results in a significant amount of metadata stored at the global level for a single object. Therefore, some implementations use a hierarchical chunking scheme, which reduces the amount of global metadata stored for each object. Within a hierarchical implementation, the term “chunk” is used to identify a top level split, which has corresponding metadata stored at the global level. In these implementations, the term “block” is used to identify a basic unit of actual storage (e.g., 2 megabytes or 8 megabytes). The blocks are managed locally for each shard. In a non-hierarchical system the single term “chunk” may be used to identify both concepts because the basic unit of storage is the basic unit for which global metadata is stored.

Hierarchical chunking can be implemented in multiple ways. In some implementations, each chunk comprises a list of blocks, even when there is only one block. In these implementations, there is always an additional hierarchical level for lookup of data corresponding to a chunk. Other implementations use a hybrid scheme so that there is a hierarchy only when needed for large chunks. In such a hybrid implementation, small objects may comprise a single chunk, which corresponds to a single block. On the other hand, for larger objects, each chunk is a list of blocks.

The disclosed hierarchical schemes reduce the amount of global metadata, which reduces the cost of managing objects or moving objects from one storage cluster to another. Whereas the object chunks are managed at the global level, the blocks within a chunk are managed at the local shard level so that the object metadata typically contains just one chunk reference per shard.

In some implementations, the upload process follows these steps: (1) find an available shard for upload; (2) write data to the current shard until either the shard is unavailable (e.g., full) or there is no more data; (3) add the current chunk reference to the ordered list of chunks; (4) if the object upload is done, finalize the object; otherwise (5) repeat starting at step (1) for the remainder of the object.

In some implementations, reading an object from storage follows these steps: (1) for the desired object, find the set of chunk references (there is always at least one); (2) find the location of the shard based on the chunk reference; (3) read the data from the shard location(s) using the chunk identifier and the local shard metadata; (4) repeat steps 2 and 3 for each chunk reference.

For example, suppose an object upload started by writing data to shard1, and switched to shard2 when shard1 became full. (The two shards shard1 and shard2 may be at the same or different instances.) The object metadata (which is global) consists of two chunk references, whereas each shard manages an local list of blocks for each chunk. For example, each shard could store a plurality of blocks for the object. In this case, the storage is completely hierarchical: the object is split into chunks, and each chunk is split into blocks. In other implementations, one of the chunks may be split into a plurality of blocks (such a chunk is sometimes referred to as a “superchunk”), whereas another chunk may consist of a single block. In the latter case, the chunk identifier may be a block identifier.

Because shard1 and shard2 are independent of each other, their replicas may be stored at different instances. For example, shard1 may be stored at instance1 and instance2, whereas shard2 may be stored at instance1 and instance3.

This disclosed methodology substantially improves both upload service availability and storage efficiency. This methodology supports resumable uploads (e.g., when an instance goes down during upload of a large object) as well as switching to a new shard in the middle of upload (e.g., when a shard becomes full). In addition, this methodology supports writing to multiple shards simultaneously, which may improve performance significantly for very large objects. In some implementations, data for a single object may be written to two or more distinct shards at distinct instances simultaneously, two or more shards at the same instance simultaneously, and even within a single journal, two or more process threads may write distinct blocks of data to the single journal simultaneously. Of course, a distributed upload is limited by available resources. The distributed storage system has many different clients uploading objects at the same time, so a single very large object from one client is not permitted to consume too much of the available resources.

According to some implementations, a method for managing placement of object replicas in a distributed storage system is performed at a first instance of the distributed storage system. The first instance has one or more servers, each having one or more processors and memory. The memory stores one or more programs for execution by the one or more processors. The first instance receives a first object that is associated with a first placement policy. The first placement policy specifies criteria for where replicas of the first object are stored in the distributed storage system. In some implementations, each placement policy specifies a target number of object replicas and target locations for those replicas. The first instance splits the object into a plurality of object chunks and splits a first object chunk of the plurality of object chunks into a plurality of blocks. The first instance stores the plurality of blocks in a first journal whose associated placement policy matches the first placement policy. The first instance stores global metadata for the first object, which includes a list of the plurality of object chunks. The list includes a respective identifier for each of the object chunks. The first instance stores local metadata for the first object chunk, which includes a block list identifying each block of the plurality of blocks. The local metadata is associated with the first journal. The first journal is subsequently replicated to a second instance of the distributed storage system in accordance with the first placement policy. The global metadata is updated to reflect the replication, whereas the local metadata is unchanged by the replication.

According to some implementations, a method for managing placement of object replicas in a distributed storage system is performed at a first instance of the distributed storage system. The first instance has one or more servers, each having one or more processors and memory. The memory stores one or more programs for execution by the one or more processors. One or more journals are opened for storage of object chunks. Each journal is associated with a single placement policy. In some implementations, each placement policy specifies a target number of object replicas and target locations for those replicas. The first instance receives a first object comprising at least a first object chunk. The first object is associated with a first placement policy. The first object chunk comprises a first plurality of blocks. The first instance stores the first plurality of blocks in a first journal whose associated placement policy matches the first placement policy. The first journal stores only blocks for objects whose placement policies match the first placement policy. The first instance stores global metadata for the first object, which includes a first list of object chunks corresponding to the first object. The first list includes an identifier of the first object chunk. The first instance also stores local metadata for the first object chunk, which includes a block list identifying each block of the first plurality of blocks. The local metadata is associated with the first journal. For the first journal, the receiving and storing operations are repeated for a first plurality of objects whose associated placement policies match the first placement policy, until a first termination condition occurs. In some implementations, the first termination condition occurs after a predefined span of time or after the first journal has exceeded a predefined size threshold. After the first termination condition occurs, the first journal is closed, thereby preventing any additional blocks from being stored in the first journal. Subsequently, the first journal is replicated to a second instance of the distributed storage system in accordance with the first placement policy. The global metadata is updated to reflect the replication, whereas the local metadata is unchanged by the replication.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a conceptual illustration of a distributed storage system, according to some implementations.

FIG. 2 is a block diagram illustrating the elements of a distributed storage system, according to some implementations.

FIG. 3 is a block diagram of a server, according to some implementations.

FIG. 4 is a block diagram of an instance server, according to some implementations.

FIG. 5 illustrates the use of journals for storage of object chunks in accordance with some implementations.

FIG. 6 illustrates how some implementations manage the storage of a new object.

FIG. 7 illustrates the structure of an open journal in accordance with some implementations.

FIG. 8 illustrates what happens to object metadata and journal metadata when a journal is replicated from one instance to another, in accordance with some implementations.

FIGS. 9A-9C illustrate a method of managing placement of object replicas in a distributed storage system according to some implementations.

FIGS. 10A and 10B illustrate how object chunks may be further split into blocks in accordance with some implementations.

FIGS. 11A-11D illustrate an alternative method of managing placement of object replicas in a distributed storage system according to some implementations.

FIG. 12 illustrates storage for chunks in a partially hierarchical distributed storage system in accordance with some implementations.

Like reference numerals refer to corresponding parts throughout the drawings.

DESCRIPTION OF IMPLEMENTATIONS

Before discussing techniques for managing the placement of objects in a distributed storage system, it is instructive to present an exemplary system in which these techniques may be used.

Distributed Storage System Overview

As illustrated in FIG. 1, the disclosed implementations describe a distributed storage system. There are multiple instances 102-1, 102-2, . . . 102-N at various locations on the Earth 100, connected by network communication links 104-1, 104-2, . . . 104-M. Note that an “instance” is also referred to as a “storage location” in this specification. Also note that one or more instances (storage locations) may be located at a particular physical location (e.g., a building, a set of buildings within a predetermined distance of each other, etc.). In some implementations, an instance (such as instance 102-1) corresponds to a data center. In some implementations, multiple instances are physically located at the same data center. A single implementation may have both individual instances at distinct geographic locations as well as one or more clusters of instances, where each cluster includes a plurality of instances, and the instances within each cluster are at a single geographic location.

Although the conceptual diagram of FIG. 1 illustrates a particular number of network communication links 104-1, etc., typical implementations may have more or fewer network communication links. In some implementations, there are two or more network communication links between the same pair of instances. For example, the network communication links 104-5 and 104-6 provide network connectivity between instance 102-2 and instance 102-6. In some implementations, the network communication links include fiber optic cable. In some implementations, some of the network communication links use wireless technology, such as microwaves. In some implementations, each network communication link has a specified bandwidth and/or a specified cost for the use of that bandwidth. In some implementations, statistics are maintained about the transfer of data across one or more of the network communication links, including throughput rate, times of availability, reliability of the links, etc. Each instance typically has data stores and associated databases, and utilizes a farm of server computers (“instance servers” as illustrated in FIG. 4) to perform all of the tasks. In some implementations, one or more instances of the distribute storage system has limited functionality. For example, the limited functionality may include acting as a repeater for data transmissions between other instances. Note that limited functionality instances may or may not include any of the data stores.

FIG. 2 is a block diagram illustrating the elements of a distributed storage system 200, according to some implementations. The distributed storage system 200 includes instances 102-1, 102-2, 102-3, 102-4, . . . 102-N. A respective instance 102-1 includes a replication module 220 that replicates object chunks 238 between instances. In some implementations, the object chunks 238 are stored in data stores 224 of the respective instance 102-1. Each object chunk 238 comprises an object 226 or a portion of an object 226, as illustrated in FIG. 6. The data stores 224 may include distributed databases, file systems, tape backups, and any other type of storage system or device capable of storing objects. In some implementations, the replication module 220 uses one or more replication queues 222-1, 222-2, . . . , 222-L to replicate objects 226 or journals 230. Replication requests for objects or journals to be replicated are placed in a replication queue 222, and the objects or journals are replicated when resources (e.g., bandwidth) are available. In some implementations, replication requests in a replication queue 222 have assigned priorities, and the highest priority replication requests are replicated as bandwidth becomes available.

In some implementations, a background replication process creates and deletes copies of objects or journals based on placement policies 212 and access data 210 and/or a global state 211 provided by a statistics server 208. The placement policies 212 specify how many copies of an object are desired, where the copies should reside, and in what types of data stores the data should be saved. Using placement policies 212, together with the access data 210 (e.g., data regarding storage locations at which replicas of objects were accessed, times at which replicas of objects were accessed at storage locations, frequency of the accesses of objects at the storage locations, etc.) and/or the global state 211 provided by the statistics server 208, a location assignment daemon (LAD) 206 determines where to create new copies of an object or journal and what copies may be deleted. When new copies are to be created, replication requests are inserted into a replication queue 222. In some implementations, the LAD 206 manages replicas of objects or journals globally for the distributed storage system 200. In other words, there is only one LAD 206 in the distributed storage system 200. The use of the placement policies 212 and the operation of a LAD 206 are described in more detail below.

Note that in general, a respective placement policy 212 may specify the number of replicas of an object to save, in what types of data stores the replicas should be saved, storage locations where the copies should be saved, etc. In some implementations, a respective placement policy 212 for an object includes criteria selected from the group consisting of a minimum number of replicas of the object that must be present in the distributed storage system, a maximum number of the replicas of the object that are allowed to be present in the distributed storage system, storage device types on which the replicas of the object are to be stored, locations at which the replicas of the object may be stored, locations at which the replicas of the object may not be stored, and a range of ages for the object during which the placement policy for the object applies. For example, a first placement policy may specify that each object in a webmail application must have a minimum of 2 replicas and a maximum of 5 replicas, wherein the replicas of the objects can be stored in data centers outside of China, and wherein at least 1 replica of each object must be stored on tape. A second placement policy for the webmail application may also specify that for objects older than 30 days, a minimum of 1 replica and a maximum of 3 replicas are stored in the distributed storage system 200, wherein the replicas of the objects can be stored in data centers outside of China, and wherein at least 1 replica of each object must be stored on tape.

In some implementations, a user 240 interacts with a user system 242, which may be a computer system or other device that can run a web browser 244. A user application 246 runs in the web browser, and uses functionality provided by database client 248 to access data stored in the distributed storage system 200 using a network. The network may be the Internet, a local area network (LAN), a wide area network (WAN), a wireless network (WiFi), a local intranet, or any combination of these. In some implementations, the database client 248 uses information in a global configuration store 204 to identify an appropriate instance to respond to the request. In some implementations, user application 246 runs on the user system 242 without a web browser 244. Exemplary user applications include an email application and an online video application.

In some implementations, each instance stores object metadata 228 for each of the objects stored in the distributed storage system. Some instances store object metadata 228 only for the objects that have replicas stored at the instance (referred to as a “local instances”). Some instances store object metadata 228 for all objects stored anywhere in the distributed storage system (referred to as “global instances”). The object metadata 228 is described in more detail with respect to FIGS. 3, 4, and 5.

In some implementations, each instance stores journal metadata 236 for each of the journals stored in the distributed storage system 200. Some instances store journal metadata 236 only for the journals that have replicas stored at the instance. Some instances store journal metadata for all journals stored anywhere in the distributed storage system. The journal metadata is described in more detail below with respect to FIGS. 3, 4, 5, and 8.

Stored in the data stores 224 are multiple types of journals. The majority of the journals are closed journals 230. Closed journals 230 do not store any additional object chunks, but can have content deleted and compacted. In some implementations, two or more small closed journals 230 for the same placement policy 212 can be stitched together to form a single replacement closed journal 230. Because data within a closed journal 230 can be deleted and compacted, closed journals 230 can get smaller over time, and thus become candidates for stitching.

In addition to the closed journals 230, an instance 102 can have open journals 232 and 234. As indicated in FIG. 2, open journals are designated as either primary journals 232 or secondary journals 234. Primary journals 232 and secondary journals 234 come in pairs, and are located at distinct instances. As described in more detail below, a primary journal 232 receives a chunk 238 for storage and transmits a copy of the chunk 238 to the instance where the corresponding secondary journal 234 is stored.

FIG. 3 is a block diagram of a server 300, according to some implementations. The server 300 typically includes one or more processing units (CPU's) 302, a clock 303 that reports the current date and/or time, one or more network or other communications interfaces 304, memory 314, and one or more communication buses 312 for interconnecting these components. The communication buses 312 may include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. In some implementations, the clock 303 is a local clock that is periodically synchronized with a clock server (e.g., a quorum clock server or any other clock server on a network, etc.). The server 300 optionally may include a user interface 306 comprising a display device 308 and input devices 310 (e.g., keyboard, mouse, touch screen, keypads, etc.). Memory 314 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 314 may optionally include one or more storage devices remotely located from the CPU(s) 302. Memory 314, or alternately the non-volatile memory device(s) within memory 314, comprises a computer readable storage medium. In some implementations, memory 314 stores the following programs, modules and data structures, or a subset thereof:

-   -   an operating system 316 that includes procedures for handling         various basic system services and for performing hardware         dependent tasks;     -   a communication module 318 that is used for connecting the         server 300 to other computers via the one or more communication         interfaces 304 (wired or wireless) and one or more communication         networks, such as the Internet, other wide area networks, local         area networks, metropolitan area networks, and so on;     -   an optional user interface module 320 that receives commands         from the user via the input devices 310 and generates user         interface objects in the display device 308;     -   the configuration 204, as described herein;     -   the LAD 206, as described herein;     -   access data 210, as described herein;     -   the global state 211, as described herein;     -   the placement policies 212, as described herein;     -   object metadata 228 for the objects stored in the distributed         storage system. The object metadata 228 may include an object ID         330, which uniquely identifies the object within the distributed         storage system. The metadata 228 may include the author 332 of         the object, which may be a name and/or identifier of a person or         entity (e.g., email address). In some implementations, the         identifier is unique. The metadata may include a datestamp or         timestamp 334 when the object was created (e.g., uploaded to the         distributed storage system). The metadata may include the size         336 of the object, which is typically measured in bytes or         allocation blocks. The metadata includes an assigned placement         policy 338, which may be assigned individually or based on other         criteria (e.g., all videos uploaded from the United States may         have the same assigned placement policy 338). The usage of         placement policies is described in more detail below with         respect to FIGS. 5-6 and 9A-9C. The metadata 228 includes a set         of chunk ID's 346 that identify the content chunks for each         object. In some implementations, a chunk ID is specified as an         offset within an object. For example, the first chunk has an         offset of 0. In some implementations, the offsets are specified         in megabytes. In some implementations, the chunk ID's are unique         identifiers (such as a GUID). In some implementations, each         chunk ID is formed by concatenating the object ID with the         offset of the chunk. In some implementations, the chunk ID if         formed using a content hash or content digest. Corresponding to         each chunk ID is an assigned journal ID 348, which indicates in         which journal the corresponding chunk is stored; and     -   journal metadata 236 for each journal stored in the distributed         storage system 200. The journal metadata 236 includes a journal         ID 370 for each journal and a set of journal locations 372 where         the journal is stored. The journal locations 372 specify each         instance 102 where the journal is stored any may specify the         data store 224 at the instance 102 that stores the journal. The         journal metadata 236 also includes the placement policy ID 374         associated with each journal. The placement policy ID 374         identifies the unique placement policy 212 associated with the         journal.

Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The set of instructions can be executed by one or more processors (e.g., the CPUs 302). The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 314 may store a subset of the modules and data structures identified above. Furthermore, memory 314 may store additional modules and data structures not described above.

Although FIG. 3 shows a “server,” FIG. 3 is intended more as functional description of the various features that may be present in a set of servers 300 than as a structural schematic of the implementations described herein. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated. For example, some items shown separately in FIG. 3 could be implemented on single servers and single items could be implemented by one or more servers. The actual number of servers and how features are allocated among them will vary from one implementation to another, and may depend in part on the amount of data traffic that the system must handle during peak usage periods as well as during average usage periods. In some implementations, a subset of the LAD 206, the access data 210, the global state 211, and the placement policies 212 are located on separate servers. For example, the LAD 206 may be located at a server (or set of servers), the access data 210 and the global state 211 may be located and maintained by a statistics server 208 (or a set of statistics servers 208), and the placement policies 212 may be located on another server (or a set of other servers).

FIG. 4 is a block diagram of an instance server 400 for an instance 102, according to some implementations. The instance server 400 typically includes one or more processing units (CPU's) 402 for executing modules, a clock 403 that reports the current date and/or time, programs and/or instructions stored in memory 414 and thereby performing processing operations, one or more network or other communications interfaces 404, memory 414, and one or more communication buses 412 for interconnecting these components. In some implementations, the clock 403 is a local clock that is periodically synchronized with a clock server (e.g., a quorum clock server or any other clock server on a network, etc.). In some implementations, the instance server 400 includes a user interface 406 comprising a display device 408 and one or more input devices 410. In some implementations, memory 414 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices. In some implementations, memory 414 includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. In some implementations, memory 414 includes one or more storage devices remotely located from the CPU(s) 402. Memory 414, or alternately the non-volatile memory device(s) within memory 414, comprises a computer readable storage medium. In some implementations, memory 414 or the computer readable storage medium of memory 414 stores the following programs, modules and data structures, or a subset thereof:

-   -   an operating system 416 that includes procedures for handling         various basic system services and for performing hardware         dependent tasks;     -   a communications module 418 that is used for connecting the         instance server 400 to other instance servers or computers via         the one or more communication network interfaces 404 (wired or         wireless) and one or more communication networks, such as the         Internet, other wide area networks, local area networks,         metropolitan area networks, and so on;     -   an optional user interface module 420 that receives commands         from the user via the input devices 410 and generates user         interface objects in the display device 408;     -   a replication module 220 and replication queues 222, as         described herein;     -   data stores 224 (e.g., distributed databases, file systems, tape         stores, Big Tables, etc.) that store the object chunks 238 in         journals 230, 232, and 234 as described with respect to FIG. 3;     -   object metadata 228 and corresponding metadata elements 330-338,         346, and 348 as described in FIG. 3 with respect to server 300;         and     -   journal metadata 236 and corresponding journal metadata elements         370, 372, and 374 as described in FIG. 3 with respect to server         300.

Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The set of instructions can be executed by one or more processors (e.g., the CPUs 402). The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 414 may store a subset of the modules and data structures identified above. Furthermore, memory 414 may store additional modules and data structures not described above.

Although FIG. 4 shows an “instance server,” FIG. 4 is intended more as functional description of the various features that may be present in a set of instance servers 400 than as a structural schematic of the implementations described herein. In practice, and as recognized by those of ordinary skill in the art, items shown separately could be combined and some items could be separated. For example, some items shown separately in FIG. 4 could be implemented on single servers and single items could be implemented by one or more servers. The actual number of servers and how features are allocated among them will vary from one implementation to another, and may depend in part on the amount of data traffic that the server must handle during peak usage periods as well as during average usage periods. For example, at a single instance 102 there may be a hundred instance servers 400 or thousands of instance servers 400.

In some implementations, to provide faster responses to clients and to provide fault tolerance, each program or process that runs at an instance is distributed among multiple computers. The number of instance servers 400 assigned to each of the programs or processes can vary, and depends on the workload.

FIG. 5 illustrates the use of journals for storage of object chunks in accordance with some implementations. FIG. 5 shows a data store 224, as well as a portion of the object metadata 228 and a portion of the journal metadata 236, all at an example instance 102. There are many journals 230, 232, and 234 stored in this data store 224, so it is useful to organize them visually in a two dimensional grid. (Of course the visual display is irrelevant to the actual physical storage of journals in a data store.) In the figure, the journals are partitioned into “rows” of journals, where each row corresponds to a single placement policy 212. For example, the first row 502-P1 corresponds to placement policy P1 (212), and includes closed journals 230, open primary journals 232, and open secondary journals 234. All of these journals in the first row 502-P1 are associated with the placement policy P1. The second row 502-P2 corresponds to placement policy P2 (212), and the last row 502-PN corresponds to placement policy PN (212). Typically the number of placement policies is small, such as 10, 20, 50, or perhaps 100. When the number of placement policies grows, management of object replicas becomes less efficient.

The journals in the data store 224 are also partitioned visually into two columns in FIG. 5. The first column identifies the closed journals 230, which is the majority of the journals. The second column includes the open primary journals 232 and the open secondary journals 234. As illustrated by the various rectangles 238 in each journal, each journal (whether closed 230, open primary 232, or open secondary 234) contains object chunks 238. The object chunks can be various sizes, but implementations typically set a fixed maximum size (e.g., 2 megabytes, 4 megabytes, or 8 megabytes). The illustration of object chunks 238 within a journal correctly conveys the fact that a journal stores many object chunks of various sizes, but is otherwise not representative of the actual physical storage of object chunks (e.g., there is generally no unused space between object chunks because each new object chunk 238 is appended at the beginning of the unallocated space).

FIG. 5 illustrates that various combinations of open journals 232 and 234 are possible for each placement policy. To identify the different journals replicas in the figures and descriptions herein, a three part label is sometimes used, such as “232.P4.7”. The first portion (e.g., “232”) identifies the type of journal (230=closed, 232=open primary, 234=open secondary); the second portion (e.g., “P4”) specifies the placement policy for the journal; and the third portion (e.g., “7”) just specifies a sequential number for the journal (e.g., the “7” in “232.P4.7” specifies the seventh open journal for placement policy P4).

As illustrated in FIG. 5, for placement policy P1 there is a single open primary journal 232.P1.1, and no open secondary journals. For placement policy P2, there are two open primary journals 232.P2.1 and 232.P2.2. For placement policy PN, there is one open primary journal 232.PN.1 and one open secondary journal 234.PN.1. As these examples illustrate, the number of open primary journals 232 and open secondary journals 234 can vary between placement policies, and is typically configured for each policy 212 based on the expected number of new objects 226 for each placement policy 212 and the desired locations for those objects 226

Each instance 102 also stores both object metadata 228 and journal metadata 236, as previously described with respect to FIG. 3. For each object 226, the object metadata 228 includes the object ID 330 (which uniquely identifies the object), a set of one or more chunk IDs 346 that identify the object chunks 238 from the object, and an assigned journal ID 348 associated with each chunk ID 236. When an object has multiple chunks 238, the chunks 238 are not necessarily all stored in the same journal (e.g., for load balancing), so the object metadata 228 must track the journal ID 348 assigned to each chunk ID 346.

Each instance 102 also stores journal metadata 236 for each journal stored at the instance 102. The metadata 236 includes a journal ID 370 for each journal, as well as a set of locations 372. In some implementations, a location ID identifies an instance where the journal is stored. In some implementations, a location ID also identifies a data store at the specified instance. In some implementations, an instance identifier and a data store identifier are stored as separate attributes for each journal. In some implementations, a journal may be stored in two or more data stores at a single instance (e.g., a file system data store and a tape backup data store). The journal metadata 236 also includes a placement policy ID 374 that specifies the unique placement policy 212 corresponding to each journal. Each journal stores only object chunks 238 whose placement policies 338 match the placement policy of the journal.

FIG. 6 illustrates how some implementations manage the storage of a new object 226. As illustrated in FIG. 6, each new object has object content (i.e., the object 226 itself), as well as an object ID 330 (e.g., 58440912) and an assigned placement policy 330 (e.g., P3). The new object 226 can come from many different applications 246, such as an online email application, a video sharing website, and so on. The distributed storage system 200 receives the new object 226 and directs (602) the new object 226 to an appropriate instance, such as the instance 102-1. In some implementations, the application 246 directs the new object 226 to a specific instance 102-1. When the instance 102-1 selected by the application 246 is not proper, some implementations forward the object 226 to an appropriate instance (e.g., if the placement policy 212 specifies no storage in Europe, and the object 226 is received at an instance in Europe, the instance can forward the object 226 to another instance).

Although most objects have moderate size (e.g., less than 300 kilobytes), there are some objects that are large. Some implementations split (604) large objects into multiple chunks 238. In general, each implementation sets a chunk size or has a configurable parameter to set the chunk size, which is typically specified in megabytes (e.g., 2, 4, 8, 16, or 32 megabytes). Each object that is larger than the chunk size is split into multiple chunks, and each object that has size equal to or less than the chunk size consists of a single chunk. In the illustration in FIG. 6, there are three chunks C1, C2, and C3. In this illustration, each of the chunks has a 7 character alphanumeric chunk ID 346, but many alternative chunk ID formats are possible that uniquely identify the chunks within each object. In some implementations, a chunk ID 346 is generated using a content hash or content digest.

In some implementations there can be many object duplicates (e.g., an email attachment sent to a group of people, then forwarded to many additional people), so de-duplication can be useful for efficient storage. Thus, in some embodiments, the content of each new chunk 238 is compared (606) to existing object chunks 238 (e.g., using a content hash or content digest) to store only (606) “new” chunks 238 in an open primary journal. As illustrated in FIG. 5, chunk C2 is new, and corresponds to placement policy P3, so chunk C2 is stored in an open primary journal 232.P3.1 corresponding to placement policy P3. Of course de-duplication is only within the context of a placement policy. If two chunks are identical, but are assigned to different placement policies, then the two chunks will be saved in distinct journals. Stated differently, when a new chunk is received, it is only compared against chunks for the same placement policy. A chunk is a “duplicate” only when there is already a saved identical chunk for the same placement policy.

Regardless of whether the object chunk C2 is new, the instance 102-1 stores (608) object metadata 228 for the chunk 238. As described previously with respect to FIGS. 3-5, the metadata 228 includes the object ID 330, the chunk ID 346, and the journal ID 348 for the journal where each chunk is stored. In some implementations, the chunk ID 346 for an object chunk 238 is just the offset to the start of the chunk 238 within the object. The object metadata 228 shown in FIG. 6 also illustrates that the chunks for a single object need not be stored in the same journal. The chunks C1 and C3 (chunk IDs C190056 and C098663) are in the journal 232.P3.2 with journal ID J77298045, whereas chunk C2 (chunk ID C250116) is in the journal 232.P3.1 with journal ID J82117094.

The chunk C2 is transmitted (610) to instance 102-2 for storage in secondary journal 234.P3.1, and chunks C1 and C3 are transmitted (612) to instance 102-2 for storage in secondary journal 234.P3.2.

FIG. 6 also illustrates that a primary journal 232 need not be physically identical to its corresponding secondary journal. First, we see that chunks C1 and C3 are stored in that order in the primary journal 232.P3.2, whereas these chunks are stored in the reverse order in the secondary journal 234.P3.2. While a journal is open, the individual chunks 238 may be replicated independently, traverse different network paths, or be processed by different processors 402, so there is no guarantee that they are loaded into the secondary journal 234.P3.2 in the same order. The fact that there can be different orders is handled by the chunk index within each journal as described below with respect to FIG. 7. In addition, primary journal 232.P3.1 indicates the presence of a garbage “chunk” 620 labeled as “G” in the figure. Sometimes during an upload there can be failure or glitch that consumes space. For example, during an upload, perhaps the space for an object is allocated, but the chunk is not actually appended. The software retries the upload, which allocates new space for the chunk. This can leave holes or garbage within a journal 232. In this case the garbage 620 is not transmitted to the secondary journal, so the primary journal is physically different from the secondary journal.

FIG. 7 illustrates the structure of an open journal in accordance with some implementations. Although FIG. 7 describes an open primary journal 232, the structure or an open secondary journal 234 would be the same or similar. A journal 232 has a header 702 and a block of storage space 714. The storage space 714 includes a filled portion 710 that is already storing object chunks 238, and an unfilled portion 712 that is currently unused. These descriptors are not completely accurate for a few reasons. First, the “filled” space 710 may include garbage portions 620 that have no useful content. Second, the unused space is not necessarily allocated all at the same time. Some implementations do allocate the entire space for the journal at one time, and close the journal when it is filled (potentially leaving a small amount of unused space at the end). But in other implementations, blocks of additional space are allocated as needed, until the journal reaches a certain size limit or a certain amount of time has elapsed (e.g., one day).

The header 702 for the journal contains important internal information about the journal 232. The header 702 includes a field 704 that specifies where the unused space 712 begins in the journal. Each time a new chunk 238 is appended to the end of the filled space 710, the offset 704 is incremented by the size of the chunk 238 so that the journal 232 is prepared to store the next chunk.

The header 702 also includes a chunk index 706. The chunk index 706 for a journal 232 specifies where each chunk 238 is located within the journal 232 as well as its size, enabling a rapid read of the chunk data (whether from non-volatile storage or from cache). The key for the chunk index 706 is the chunk ID 346, which uniquely identifies the chunk. Note that multiple distinct object ID's 330 may refer to the same physical chunks. To avoid a huge chunk index 704 with many entries pointing to the same object chunk 238, implementations typically utilize a single chunk ID to refer to the same physical content. For example, the chunk ID 346 may be a content hash or a content digest (or a combination of these). For each chunk ID 346, the chunk index 720 specifies an offset 720 and a size 722 for the chunk 238 within the storage space 714. The offset 720 may be specified either as an offset from the beginning of the journal 232 or an offset from the beginning of the filled space 710. In some implementations, the chunk index has additional information, such as a deletion marker that is used later when chunks are deleted and the filled space 710 compacted.

The header 702 may contain other journal data 708 as well to address implementation details. For example, the other journal data 708 may specify the offset from the beginning of the journal to the beginning of the storage space 714 (i.e., the size of the header). In some implementations, the other journal data includes a “time to live” parameter for journals that are designated to have a short lifespan.

Although the structure of the journal in FIG. 7 is for an open primary journal 232, the same basic structure applies to open secondary journals 234 and closed journals 230 as well.

FIG. 8 illustrates what happens to object metadata 228 and journal metadata 236 when a journal is replicated from one instance to another, in accordance with some implementations. In this illustration, closed journal 230 with journal ID J82117094 is replicated (820) from instance 102-1 (with instance ID=723) to instance 102-4 (with instance ID 428). Because the journal 230 itself is replicated as a unit, the entire content is replicated exactly. For example, chunk C8 (with chunk ID C408335) is in exactly the same position within the journal. Of course after replication, instance 102-1 and 102-4 independently handle deletion and compaction, so their physical structures are not guaranteed to stay the same after replication.

FIG. 8 also shows a portion of the object metadata 228 and journal metadata 236, both before and after the replication 820. As indicated, the records 802-814 in the object metadata 228 are unchanged by the replication 820. Each object 226 has the same chunks 238, and the chunks 238 are stored in the same journal 230. For example, the chunk with chunk ID C408335 (in row 804) is unchanged. On the other hand, the journal metadata 236 for the journal 230 with journal ID J82117094 (370-1) does change. The set of journal locations 372 changes from 372-1(A) to 372-1(B), which includes the new location 428 (for instance 102-4).

FIGS. 9A-9C illustrate a method 900 of managing (902) placement of object replicas in a distributed storage system 200 according to some implementations. The method is performed (904) at a first instance 102 of the distributed storage system, which has one or more processors and memory. The memory stores (906) a plurality of objects. The memory also stores (908) one or more programs for execution by the one or more processors. In some implementations, all or part of method 900 is performed by location assignment daemon 206. In some implementations, the distributed storage system has (910) a plurality of instances. In some of these implementations, at least a subset of the instances are (910) at distinct geographic locations. In some implementations, each instance corresponds to a data center. In some implementations, each data center comprises one or more instances.

At the first instance, one or more journals 232 are opened (912) for storage of object chunks. Each journal is associated with (914) a single respective placement policy 212. In some implementations, each placement policy specifies (926) a target number of object replicas and a target set of locations for the object replicas. In some implementations, a placement policy 212 may specify what type of data store 224 to use at some of the instances (e.g., on disk or on tape). In some implementations, the distributed storage system 200 includes (918) object metadata 228 that specifies in which journal each object chunk 238 is stored. This was described previously with respect to FIGS. 3-5. In some implementations, each respective journal includes (920) a chunk index 706 that specifies the location of each object stored in the respective journal. This was described in more detail in FIG. 7. In particular, the location of each chunk within a journal is identified relative to the journal itself, and thus the chunk index 706 is accurate regardless of where the journal is stored. For example, by specifying the location of chunks within a journal as offsets, the chunks can be accessed by relative addressing.

Disclosed implementations typically include (922) journal metadata 236 that specifies the locations 372 where each journal is stored. This was described previously in FIGS. 3-5 and 8.

The distribution of open primary journals 232 and open secondary journals 234 depends on many factors, including the available instances 102, the placement policies 212, the anticipated distribution of new objects 226 with the placement policies 212, where the new objects are loaded from (e.g., Europe, North America, Asia), processing resources at each of the available instances 102, and the network bandwidth between the various instances. For example, if many objects will be uploaded with a specific placement policy at a specific instance, then multiple journals are opened (924) for the same placement policy at that instance. In some scenarios, there may be 5, 10, or more open journals for the same placement policy 212 at a single instance 102 when required for load balancing.

As described previously with respect to FIGS. 5 and 6, some implementations transmit (916) a message to a third instance of the distributed storage system 200 to open journals corresponding to journals opened at the first instance. In this scenario, the journals 232 opened at the first instance are referred to as primary journals and the journals 234 opened at the third instance are referred to as secondary journals. (Of course the first instance could also have secondary journals and the third instance could have primary journals.)

At the first instance 102, a first object 226 is received (928), which comprises (928) at least a first object chunk. This was described above with respect to FIG. 6. The first object 226 is associated with a first placement policy 212, and thus all of the object chunks 238 that comprise the object 226 are associated with the first placement policy 212. The first object chunk 238 is stored (930) in a first journal 232 whose associated placement policy matches the first placement policy 212. The first journal 232 stores only (932) object chunks for objects whose placement policies match the first placement policy. In some implementations, each object chunk 238 stored in the first journal 232 is transmitted (934) to the third instance for storage in a third journal 234.

When the received object is larger than the chunk size, the object is split into multiple chunks 238. In this case, the first object 226 comprises (936) two or more object chunks. Typically the second object chunk is distinct from (936) the first object chunk. (Having two identical chunks within a single object is rare, but could happen, for example, if an object had a very large portion of empty space.) In some circumstances, the second object chunk is stored (938) in a second journal 232, distinct from the first journal, whose associated placement policy matches the first placement policy. The second journal stores only (938) object chunks for objects whose placement policies match the first placement policy. In this way, a object that comprises many chunks could have the chunks distributed across many different journals.

This process of receiving objects 226 and storing the chunks 238 in the first journal 232 is repeated (940) for a plurality of objects 226 whose associated placement policies 338 match the first placement policy 212, until a first termination condition occurs. In some implementations, the first termination condition occurs when (942) the size of the first journal exceeds a predefined threshold. In some implementations, the first termination condition occurs when (944) the first journal has been open for a predefined span of time. Some implementations combine size and time in various ways. For example, some implementations specify both a time span and a size limit, and the termination condition is whichever one occurs first.

After the termination condition occurs, the first journal is closed (946), thereby preventing any additional object chunks from being stored in the first journal 232. Generally, implementations confirm that other journals 232 for the same placement policy are still open (or a new one is opened) prior to closing the first journal. Because new objects can arrive at any moment, it is important to have open journals available for storage. When there is a corresponding secondary journal 234 at another instance, the first instance transmits (948) a message to the other instance to close the corresponding secondary journal when the first termination condition occurs.

After the first journal 232 is closed, the journal is subject to its placement policy. Satisfying the placement policy 212 may require moving a journal replica, making a new copy of a journal replica, or deleting a replica of a journal. In some circumstances, the first journal 232 is replicated (950) to a second instance 102 of the distributed storage system 200 in accordance with the placement policy 212. (In other circumstances, a replica of the first journal is deleted.) In implementations that have primary and secondary open journals 232 and 234, there will be two equivalent closed journals 230 once they are closed. Therefore, either of the replicas could be used as the source for the replication 950. As the replication 950 occurs (i.e., as part of the transaction), the journal metadata 236 for the first journal is updated (952) to indicate that there is a copy of the journal at the second instance. This was described above with respect to FIG. 8.

After a journal 230 is closed, the object chunks 238 may be deleted. For example, an object may correspond to an email attachment. If the recipient of the email deletes the email, then the storage for the attachment can be deleted. After a period of time, there are holes within each journal from the deletions, and thus it is useful to compact the journal to remove the wasted space. This is similar to fragmentation of volatile memory and the process of defragmentation to consolidate the unused space into larger contiguous blocks.

Because a stored object chunk may correspond to many distinct objects (e.g., hundreds, thousands, or millions), an object chunk in a journal can only be deleted if there are no more references to it. Therefore, once a first closed journal 230 is selected (954), the process 900 identifies (956) one or more object chunks stored in the first closed journal 230 for which there are no references in the object metadata 228. For these identified chunks 238, the chunk index 706 is updated (958) to remove the corresponding records. In some implementations, the space previously allocated to the identified object chunks are overwritten (e.g., each byte set to ASCII 0), but in other implementations the space is just no longer referenced. In some implementations, the deallocated storage space is tracked as part of the other journal data 708. For example, some implementations maintain a list of deallocated storage spaces (e.g., offset and size), or track the deallocated spaces as a linked list.

In some implementations, a garbage collection algorithm runs periodically to compact (960) each of the closed journals. The compaction process consolidates (960) the stored object chunks into a contiguous block, thus reducing the size of the journal 230. Over time, journals 230 can become small as more object chunks are deleted. Managing many small journals has overhead similar to managing individual objects, and thus the benefit of the journal storage is diminished. To address this issue, some implementations stitch together (962) two or more closed journals to form a single replacement journal, and update (962) object metadata 228 to indicate that object chunks previously stored in the two or more journals are now stored in the replacement journal. Because a stitching operation requires forming an entirely new journal and updating the metadata for all of the objects involved, stitching is usually limited to the scenario where the journals have gotten relatively small.

FIGS. 10A and 10B illustrate two implementations for storing objects and associated metadata in a distributed storage system. The implementation illustrated in FIG. 10A is fully hierarchical: every object is split into one or more chunks, and every chunk is split into one or more blocks. Note that the structure is hierarchical even when there is only one chunk or only one block. On the other hand, the implementation illustrated in FIG. 10B is only partially hierarchical. In this implementation, some chunks are “superchunks,” which refer to lists of blocks. For example, a superchunk may have a block list with 100 blocks, 1000 blocks, or even more. A chunk that is not a superchunk is just a block. That is, the chunk identifier refers to an actual storage of object data rather than a list of blocks. This hybrid approach can be useful in distributed storage systems that include both small objects (where no hierarchy is needed) and very large objects, where the storage hierarchy is much more efficient.

The global metadata 1002 includes the object metadata 228 and journal metadata 236, as illustrated in FIGS. 2-4. In some implementations, each chunk ID 346 is assigned a decryption key 1040, which is used to decrypt the data for the chunk. In these implementations, the same decryption key would apply to all blocks in a chunk for those chunks that are split into multiple blocks. Each chunk has its own decryption key 1040, which is effectively unique. Some implementations guarantee uniqueness when new keys are generated, but some implementations generate new keys randomly, with repetition of keys being highly improbable. The decryption key 1040 corresponds to an encryption key that is used to encrypt new objects as they are stored. Because the decryption key 1040 is needed to access each object chunk, deleting the decryption key can be used as a “soft” delete of an object chunk. When the decryption key is gone, the encrypted storage is “garbage,” and the actual data is inaccessible. This can allow a garbage collection algorithm more time between compactions, and the garbage collection process can recover more storage space when it does run.

Also illustrated in FIG. 10A is a journal 232 (which is shown as open), and corresponding local metadata 1004. In some implementations, the local metadata 1004 for a journal 232 is stored in the journal itself, as part of the header 702. In other implementations, the local metadata 1004 for a journal is stored as a separate file (or in a database, etc.) and associated with the journal. The structure of a journal 232 for non-hierarchical storage was illustrated above with respect to FIG. 7. In this implementation, rather than storing chunks, the basic unit of storage is a block 1016, such as blocks 1016-1, 1016-2, . . . , 1016-N. Each implementation typically specifies a maximum block size, such as 2 megabytes, 4 megabytes, 8 megabytes, or 16 megabytes.

As noted above, the local metadata 1004 may be stored in the header 702 of the journal 232, or may be stored separately. For each chunk identifier 346, there is a corresponding block list 1006 (typically a unique block list), which comprises one or more block identifiers 1008. For a small chunk, the block list 1006 may contain a single block identifier 1008. The local metadata 1004 also includes a block index 1010, which specifies where each block is located within the journal 232. In some implementations, the location of a block is specified by an offset and a size. The block offset 1012 in some implementations is the offset from the beginning of the storage space 714 or the offset for the beginning of the journal file 232. Typically the block size 1014 is specified in bytes, but other implementations use alternative basic units of size (e.g., 2 bytes, 4 bytes, or 8 bytes). One aspect of the local metadata is that it does not change when a journal is moved or replicated to another instance: the block list 1006 for a chunk remains the same, the block ID's 1008 remain the same, the block offsets 1012 within the journal remain the same, and the block sizes remain the same.

FIG. 10B is similar to FIG. 10A, but illustrates a partially hierarchical structure. In the partially hierarchical structure of FIG. 10B, the global metadata 1002 includes a “superchunk” field 1020 that indicates whether each chunk is an ordinary block or refers to a list of blocks (i.e., is a superchunk). In some implementations, most objects are small, consisting of a single chunk. In this case, the chunk ID 346 identifies a block directly in the chunk/block index 1024. That is, the chunk ID 346 is a chunk/block ID 1026. Thus, for chunks that are not superchunks, the chunk ID 346 can be used to look up the appropriate record in the chunk/block index 1024 to find the offset 1028 and size 1030 for the corresponding block 1016 in the journal 232.

For superchunks, the chunk ID 346 is a (super) chunk ID 1022, which can be looked up in the local metadata 1004. Corresponding to the super chunk ID 1022 is a block list 1006, which comprises a set of block ID's 1008. In this case, each of the block ID's can be looked up in the chunk/block index 1024 to identify the offset 1028 and size 1030 for each of the block ID's 1026 in the block list 1006 for the super chunk ID 1022. As before, the offset 1028 and size 1030 identify the location of the actual block storage in the storage space 714 of the journal 232. Superchunks thus have an extra level of hierarchy, but reduce the amount of chunk metadata stored in the global metadata 1002. This makes is easier and more efficient to move a shard from one instance to another.

FIGS. 11A-11D illustrate a method 1100 of managing (1102) placement of object replicas in a distributed storage system 200 according to some implementations. The method is performed (1104) at a first instance 102 of the distributed storage system, which has one or more processors and memory. The memory stores (1106) one or more programs for execution by the one or more processors. In some implementations, all or part of method 1100 is performed by a location assignment daemon 206. In some implementations, the distributed storage system has (1108) a plurality of instances. In some of these implementations, at least a subset of the instances are (1108) at distinct geographic locations. In some implementations, each instance corresponds to a data center. In some implementations, each data center comprises one or more instances.

At the first instance, one or more journals 232 are opened (1110) for storage of object chunks. Each journal is associated with (1112) a single respective placement policy 212. In some implementations, each placement policy specifies (1122) a target number of object replicas and a target set of locations for the object replicas. In some implementations, a placement policy 212 may specify what type of data store 224 to use at some of the instances (e.g., on disk or on tape). In some implementations, the distributed storage system 200 includes (1114) object metadata 228 (part of the global metadata 1002) that specifies in which journal each object chunk 238 is stored. This was described previously with respect to FIGS. 3-5, 10A, and 10B. In some implementations, each respective journal includes (1116) a block index 1010 or 1026 that specifies the location of each block stored in the respective journal. This was described in more detail in FIGS. 7 (non-hierarchical), 10A, and 10B. In particular, the location of each block 1016 within a journal 232 is identified relative to the journal itself, and thus the block index 1010 or 1026 is accurate regardless of where the journal 232 is stored. For example, by specifying the location of blocks 1016 within a journal 232 as offsets, the blocks 1016 can be accessed by relative addressing.

Disclosed implementations typically include (1118) journal metadata 236 (part of the global metadata 1002) that specifies the locations 372 where each journal is stored. This was described previously in FIGS. 3-5 and 8.

The distribution of open primary journals 232 and open secondary journals 234 depends on many factors, including the available instances 102, the placement policies 212, the anticipated distribution of new objects 226 with the placement policies 212, where the new objects are loaded from (e.g., Europe, North America, Asia), processing resources at each of the available instances 102, and the network bandwidth between the various instances. For example, if many objects will be uploaded with a specific placement policy at a specific instance, then multiple journals are opened (1120) for the same placement policy at that instance. In some scenarios, there may be 5, 10, or more open journals for the same placement policy 212 at a single instance 102 when required for load balancing.

At the first instance 102, a first object 226 is received (1124), which comprises (1124) at least a first object chunk. This was described above with respect to FIG. 6. The first object 226 is associated with (1124) a first placement policy 212, and thus all of the object chunks 238 that comprise the object 226 are associated with the first placement policy 212. The first object chunk comprises (1126) a first plurality of blocks, as described above with respect to FIGS. 10A and 10B. In some implementations, the process 1100 receives (1124) the object 238 already partitioned into chunks and blocks. For example, the splitting may be performed by the client device that uploads the object. In other implementations, the process 1100 receives the object as a stream and splits the object into chunks and blocks according to stored criteria (e.g., target block and chunk size, available open journals, available instances, available bandwidth, etc.) In some implementations, dynamic allocation of chunks if performed while still receiving data for an object, whereas other implementations split an object into chunks and blocks only after the entire object is received.

The hierarchy of chunks and blocks may be formed in various ways and based on various factors, such as the size of the object. In some implementations, the hierarchy is built dynamically during the upload process. For example, a first object chunk is created, and the stream of data is split into blocks that are assigned to the first object chunk until a threshold number of blocks is assigned to the chunk. At that point, a second chunk is created, and the new blocks are added to the second chunk. In another implementation, the stream of data is stored as blocks of storage initially, and when there are no more blocks, the blocks are grouped into chunks.

In some implementations, every object chunk 238 comprises (1128) one or more blocks. This was illustrated above with respect to FIG. 10A. In some implementations, the global metadata 1002 includes (1130) a field 1020 that specifies whether each object chunk 238 is a block or a list of blocks. This is illustrated above in FIG. 10B. In some instances, the first object chunk is (1132) a list of blocks (i.e., a superchunk), whereas a second chunk is (1132) an ordinary block (not a superchunk).

The first plurality of blocks 1016 is stored (1134) in a first journal 232 whose associated placement policy matches the first placement policy 212. The first journal 232 stores only (1136) blocks for objects whose placement policies match the first placement policy.

When the received object is larger than a specified size (e.g., the chunk size or block size), the object is split into multiple chunks 238 and/or multiple blocks 1016. In some instances, the first object 226 comprises (1138) two or more object chunks. Typically the second object chunk is distinct from (1138) the first object chunk. (Having two identical chunks within a single object is rare, but could happen, for example, if an object had a very large portion of empty space.) In some circumstances, the second object chunk is stored (1140) in a second journal 232, distinct from the first journal, whose associated placement policy matches the first placement policy. The second journal stores only (1140) object chunks for objects whose placement policies match the first placement policy. In this way, a object that comprises many chunks could have the chunks distributed across many different journals.

In some implementations, the process encrypts (1142) the data for each object chunk, and stores (1142) a decryption key for each object chunk in the global metadata. This was illustrated above in FIGS. 10A and 10B. In some implementations, when a chunk is split into multiple blocks, each of the blocks within the chunk are encrypted with the same encryption key, and can thus be decrypted with the same decryption key. In other implementations, each block has its own decryption key, which may be stored as part of the block index 1010 or 1026. In implementations that store the decryption key 1040 in the global metadata 1002, a chunk can be de facto deleted simply by deleting (1144) the decryption key. The chunk is inaccessible because there is no way to retrieve the data for the original chunk. This provides some advantages. First, deleting a chunk is quick and effective. Second, because there is no real risk of accessing the deleted data, a more efficient garbage collection process can be implemented. In particular, garbage collection can be scheduled at appropriate intervals, and can batch process the physical deletes of storage from disk. Because compaction is a resource intensive process, the ability to batch together many deletes can increase efficiency dramatically. Third, some implementations do not require physical erasing of storage space because the encrypted “gibberish” cannot be converted back to meaningful content.

The process 1100 stores (1146) global metadata for the first object. This was illustrated above in FIGS. 3-5, 10A, and 10B. The global metadata 1002 includes (1148) a first list of object chunks corresponding to the first object. In particular, the first list includes (1150) an object identifier 330 for the first object chunk 238. The global metadata 1002 also identifies the journal where each chunk is stored as well the locations for each of the journals.

In addition to the global metadata 1002, local metadata 1004 is stored for each journal 232. In some implementations, the local metadata 1004 for each journal is stored in the header 702 of the journal 232 itself. In other implementations, the local metadata 1004 is stored separately from the journal. When stored separately, the local metadata 1004 for each journal may be stored separately (e.g., a distinct metadata file corresponding to each journal), or the local metadata may be grouped together (e.g., in a database).

The first instance stores (1152) local metadata 1004 for the first object chunk 238. The local metadata 1004 includes (1154) a block list identifying each block in the first plurality of blocks. Note that the block list is stored in the local metadata 1004, not in the global metadata 1002. The block list 1006 stored in the local metadata 1004 tracks how the blocks are allocated within each journal. The local metadata for the first journal 232 is associated with (1156) the first journal 232. In some implementations, the association of the local metadata with a journal is performing by storing the local metadata in the journal, which makes a journal more self-contained. In some implementations, the local metadata for a journal 232 is stored separately (e.g., in a separate file), and associated with the journal (e.g., by including the journal ID 370 in the name of the journal and in the name of the associated metadata file). In implementations that store local metadata in a database, the journal ID 370 is typically part of the primary key for the metadata tables.

This process of receiving objects 226 and storing the chunks 238 in the first journal 232 is repeated (1158) for a plurality of objects 226 whose associated placement policies 338 match the first placement policy 212, until a first termination condition occurs. In some implementations, the first termination condition occurs when (1160) the size of the first journal exceeds a predefined threshold. In some implementations, the first termination condition occurs when (1162) the first journal has been open for a predefined span of time. Some implementations combine size and time in various ways. For example, some implementations specify both a time span and a size limit, and the termination condition is whichever one occurs first.

After the termination condition occurs, the first journal is closed (1164), thereby preventing any additional blocks from being stored in the first journal 232. Generally, implementations confirm that other journals 232 for the same placement policy are still open (or a new one is opened) prior to closing the first journal. Because new objects can arrive at any moment, it is important to have open journals available for storage.

After the first journal 232 is closed, the journal is subject to its placement policy. Satisfying the placement policy 212 may require moving a journal replica, making a new copy of a journal replica, or deleting a replica of a journal. In some circumstances, the first journal 232 is replicated (1166) to a second instance 102 of the distributed storage system 200 in accordance with the placement policy 212. (In other circumstances, a replica of the first journal is deleted.) In implementations that have primary and secondary open journals 232 and 234, there will be two equivalent closed journals 230 once they are closed. Therefore, either of the replicas could be used as the source for the replication 1166. As the replication 1166 occurs (e.g., as part of the transaction), the global metadata 1002 for the first journal is updated (1168) to indicate that there is a copy of the journal at the second instance. On the other hand, the local metadata 1004 is unchanged (1168) by the replication. This was described above with respect to FIGS. 8, 10A, and 10B.

After a journal 230 is closed, the object chunks 238 may be deleted. For example, an object may correspond to an email attachment. If the recipient of the email deletes the email, then the storage for the attachment can be deleted. After a period of time, there are holes within each journal from the deletions, and thus it is useful to compact the journal to remove the wasted space. This is similar to fragmentation of volatile memory and the process of defragmentation to consolidate the unused space into larger contiguous storage.

Because a stored object chunk may correspond to many distinct objects (e.g., hundreds, thousands, or millions), an object chunk in a journal can only be deleted if there are no more references to it. Therefore, once a first closed journal 230 is selected (1170), the process 1100 identifies (1172) one or more object chunks stored in the first closed journal 230 for which there are no references in the object metadata 228. In some implementations, a garbage collection algorithm runs periodically to compact (1174) each of the closed journals. The compaction process consolidates (1174) the stored blocks into contiguous storage, thus reducing the size of the journal 230.

Over time, journals 230 can become small as more object chunks are deleted. Managing many small journals has overhead similar to managing individual objects, and thus the benefit of the journal storage is diminished. To address this issue, some implementations stitch together (1176) two or more closed journals to form a single replacement journal, and update (1176) object metadata 228 to indicate that object chunks previously stored in the two or more journals are now stored in the replacement journal. Because a stitching operation requires forming an entirely new journal and updating the metadata for all of the objects involved, stitching is usually limited to the scenario where the journals have gotten relatively small.

FIG. 12 illustrates an example of storing chunks in a distributed storage system in accordance with some implementations as illustrated previously with respect to FIG. 10B. In this example, two chunks 238-1 and 238-2 are shown. Chunk 238-1 is an ordinary chunk (i.e., not a superchunk), which chunk ID 346-1. Because chunk 238-1 is an ordinary chunk, it can be looked up directly in the chunk/block index 1024. In this illustration, the chunk/block index 1024 is stored in the header 702 of the journal 232 where the data is stored. For this chunk/block, the offset 1028 is y (1028-y). Using this offset, the corresponding block B 1016-B can be found in the storage space 714.

Chunk 238-2, however, is a superchunk with (super) chunk ID 346-2. As illustrated here, the superchunk 238-2 points to an entry in the block list table 1006. For each super chunk ID 1022 there is a plurality of corresponding block ID's 1008. FIG. 12 illustrates two corresponding blocks 1008-1 and 1008-2, but for very large objects there could be a very large number of blocks for a single chunk. The block ID's 1008-1 and 1008-2 are then looked up in the chunk/block index 1024 to find the offsets 1028-x and 1028-z for the blocks. Finally, using the offsets 1028-x and 1028-z, the corresponding blocks 1016-A and 1016-C are located in the storage space 714. In this example, the two blocks are not contiguous, and in fact the block 1016-B for chunk 238-1 separates the two blocks for chunk 238-2. Of course the size of each block is also used so that only the proper data for each block is read. This was described above with respect to FIG. 10B.

Implementations that do not allow ordinary chunks (such as chunk 238-1) are fully hierarchical. Also note that the allocation between chunks and blocks varies based on implementation or other dynamic factors. For example, the same object could be stored as a single chunk with 100 blocks, or four chunks with 25 blocks each. Some implementations vary the number of chunks based on empirical feedback from actual usage.

The foregoing description, for purpose of explanation, has been described with reference to specific implementations. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The implementations were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best utilize the invention and various implementations with various modifications as are suited to the particular use contemplated. 

What is claimed is:
 1. A method for managing placement of object replicas in a distributed storage system, comprising: at a first instance of the distributed storage system, having one or more processors and memory, wherein the memory stores one or more programs for execution by the one or more processors: receiving a first object; splitting the first object into a plurality of object chunks and splitting a first object chunk of the plurality of object chunks into a plurality of blocks; storing the plurality of blocks in a first journal; storing global metadata for the first object, wherein the global metadata includes a list of the plurality of object chunks, and wherein the list includes a respective identifier for each of the object chunks; storing local metadata for the first object chunk, wherein the local metadata includes a block list identifying each block of the plurality of blocks, and wherein the local metadata is associated with the first journal; replicating the first journal to a second instance of the distributed storage system, wherein the global metadata is updated to reflect the replication, whereas the local metadata is unchanged by the replication.
 2. The method of claim 1, wherein the global metadata includes a field that specifies whether each object chunk is a block or a list of blocks, and wherein a second object chunk is a block and the first object chunk is a list of blocks.
 3. The method of claim 1, wherein the global metadata specifies in which journal each object chunk is stored, and each respective journal replica includes a block index that specifies the location of each block stored in the respective journal replica.
 4. The method of claim 1, further comprising at the first instance: selecting a replica of a first closed journal; identifying one or more object chunks stored in the replica for which there are no references in the global metadata; and compacting the replica, thereby consolidating the blocks stored in the replica into contiguous storage.
 5. The method of claim 1, wherein the distributed storage system has a plurality of instances at distinct geographic locations.
 6. The method of claim 1, wherein data for each object chunk is encrypted, and a decryption key for each object chunk is stored in the global metadata, the method further comprising de facto deleting an object chunk by deleting the corresponding decryption key from the global metadata, thereby making the data for the object inaccessible.
 7. A method for managing placement of object replicas in a distributed storage system, comprising: at a first instance of the distributed storage system, having one or more processors and memory, wherein the memory stores one or more programs for execution by the one or more processors: opening one or more journals for storage of object chunks; receiving a first object comprising a plurality of object chunks, including a first object chunk, wherein the first object chunk comprises a first plurality of blocks; storing the first plurality of blocks in a first open journal; storing global metadata for the first object, wherein the global metadata includes a first list of object chunks corresponding to the first object, and wherein the first list includes an identifier of the first object chunk; storing local metadata for the first object chunk, wherein the local metadata includes a block list identifying each block of the first plurality of blocks, and wherein the local metadata is associated with the first journal; for the first journal, repeating the receiving and storing operations for a first plurality of objects until a first termination condition occurs; after the first termination condition occurs, closing the first journal, thereby preventing any additional blocks from being stored in the first journal; and replicating the first journal to a second instance of the distributed storage system, wherein the global metadata is updated to reflect the replication, whereas the local metadata is unchanged by the replication.
 8. The method of claim 7, wherein each object chunk comprises one or more blocks.
 9. The method of claim 7, wherein the global metadata includes a field that specifies whether each object chunk is a block or a list of blocks.
 10. The method of claim 9, wherein a second object chunk is a block and the first object chunk is a list of blocks.
 11. The method of claim 7, wherein the first object comprises two or more object chunks, including a second object chunk distinct from the first object chunk, and wherein the second object chunk is stored in a second journal, distinct from the first journal.
 12. The method of claim 7, wherein the global metadata specifies in which journal each object chunk is stored, and each respective journal replica includes a block index that specifies the location of each block stored in the respective journal replica.
 13. The method of claim 7, further comprising at the first instance: selecting a replica of a first closed journal; identifying one or more object chunks stored in the replica for which there are no references in the global metadata; and compacting the replica, thereby consolidating the blocks stored in the replica into contiguous storage.
 14. The method of claim 7, wherein the distributed storage system has a plurality of instances at distinct geographic locations.
 15. The method of claim 7, wherein data for each object chunk is encrypted, and a decryption key for each object chunk is stored in the global metadata.
 16. The method of claim 15, further comprising de facto deleting an object chunk by deleting the corresponding decryption key from the global metadata, thereby making the data for the object inaccessible.
 17. A computer system for managing placement of object replicas in a distributed storage system having a plurality of instances, each respective instance comprising: one or more processors; memory; and one or more programs stored in the memory, the one or more programs comprising instructions executable by the one or more processors for: opening one or more journals for storage of object chunks; receiving a first object comprising a plurality of object chunks including a first object chunk, wherein the first object chunk comprises a first plurality of blocks; storing the first plurality of blocks in a first journal; storing global metadata for the first object, wherein the global metadata includes a first list of object chunks corresponding to the first object, and wherein the first list includes an identifier of the first object chunk; storing local metadata for the first object chunk, wherein the local metadata includes a block list identifying each block of the first plurality of blocks, and wherein the local metadata is associated with the first journal; for the first journal, repeating the receiving and storing operations for a first plurality of objects until a first termination condition occurs; after the first termination condition occurs, closing the first journal, thereby preventing any additional blocks from being stored in the first journal; and replicating the first journal to a second instance of the distributed storage system, wherein the global metadata is updated to reflect the replication, whereas the local metadata is unchanged by the replication.
 18. The computer system of claim 17, wherein the global metadata includes a field that specifies whether each object chunk is a block or a list of blocks, and wherein a second object chunk is a block and the first object chunk is a list of blocks.
 19. The computer system of claim 17, wherein data for each object chunk is encrypted, and a decryption key for each object chunk is stored in the global metadata, the method further comprising de facto deleting an object chunk by deleting the corresponding decryption key from the global metadata, thereby making the data for the object inaccessible.
 20. The computer system of claim 17, wherein the global metadata includes a field that specifies whether each object chunk is a block or a list of blocks. 